Digital content bundle

ABSTRACT

The present technology describes creating and delivering a digital content package in a specified input structure to a content server for processing before distribution to client devices. The technology includes receiving one or more creatives, a targeted application, and a manifest associated with the targeted application within the digital content package. The content server uses the manifest to prepare an archive file containing selected resources related to the targeted application. The archive can be optimistically served to a client device along with one or more creatives for display on the client device and linking to the targeted application. A user selection of one of the one or more creatives can cause execution of the targeted application. Accordingly, the present technology leverages the use of the digital content package created by content providers to process new content and serve it to client devices.

FIELD

The following relates to creating a digital content bundle and morespecifically to creating a digital content bundle for ingestion into acontent server.

BACKGROUND

Many electronic devices, including smart phones, tablet computers, andlaptop computers allow users to download and run applications. Examplesof applications that can be downloaded include, for example, games,music, and news applications. Users can download these applications froman on-line store. These applications are popular with consumers in partbecause they allow a consumer to conveniently download applications ofparticular interest to each user. Content providers desire to displaycontent targeted to the interest of the user (targeted content) withinthese applications. Displaying targeted content within a targetedapplication allows a content provider to send its targeted content tousers of specific applications, which may have more interest in thespecified content.

Content creators typically upload or digitally send their media to acontent server to make them available for distribution as targetedcontent. This process can be complicated and time consuming inasmuch asthere are many parameters and criteria that need to be met for properingestion of the media into the on-line stores.

Therefore, what is needed is a method and apparatus for generatingtargeted content configured to be ingested into a content server thatcan be operated in a simple manner.

SUMMARY

Accordingly, a method and system for receiving a package of digitalcontent at a server and processing the package into a format suitablefor distribution by the server is disclosed.

Just as in any process, whether performed on a computer or an assemblyline, a recognized input needs to be provided to result in a desiredoutput. The present technology addresses receiving a specified input andprocessing the input for use by a server before distribution to clientdevices.

In particular, the present technology relates to creation of digitalcontent, which in preferred embodiments comes in the form of a targetedapplication for execution on a computing device such as a personalcomputer, laptop, tablet, or personal media-playing device. The targetedapplication can also be accompanied by additional applications and/orsub-routines, or resources used by the targeted application.

A content developer can develop a targeted application, which can be anapplication having content that is desired to be distributed andultimately viewed by targeted users, and then package the targetedapplication and its associated files for ingestion by the server. Thisdigital content package can include a directory containing the targetedapplication and referenced files. It can also include a directory ofcreatives, which can refer to the targeted application. The digitalcontent package can also include a properties file to instruct theserver regarding various attributes about the targeted application orthe creatives and suggested platforms in which to deploy each.Additionally, the digital content package can include a manifest filefor use by the server in packaging the targeted application fordistribution to client devices.

In some embodiments, the creatives are themselves applications or imagesor files, such as html files that link to or direct a user to the fullapplication. The creatives can be displayed at the instruction of theserver. The creatives can also be displayed within other programs. Insome embodiments, the creatives can be an advertisement for the fullapplication. The server can create a full or partial webarchive for eachcreative.

In some embodiments, the properties file can instruct the server as tothe desired attributes of the creatives and the targeted application.For example, the properties file can provide a background color for acreative or direct the server to display a given creative in aparticular situation, e.g., display the creative with a sportsapplication. The properties file can also indicate that a particularcreative was created with a particular device in mind. Accordingly, theserver can learn of various intended features for display of thecreatives or of the targeted application. In some embodiments of theproperties file, the server might consider the attributes listed in theproperties file as suggestions rather than rules that must be abided.

In some embodiments of the manifest file, the targeted applicationdeveloper can designate which resources should be prepackaged fordelivery to the user. In some examples, a manifest file is only found inthe directory containing the targeted application. The server can usethe manifest file, which can list resources within the same directory,to gather the designated resources and package those resources alonginto a targeted application webarchive.

Using the package structure example described above, a content servercan prepare the various creatives and the targeted application fordistribution to a client device. When a client device requests contentfrom the content server, the server can send one or more creatives,selected by the server, to the client device. The server can optionallysend each creative within a full or partial webarchive. The server canalso send, either at the same time or immediately following thecreatives, the targeted application webarchive file. In other words, thetargeted application webarchive file can be sent optimistically.

From a client device perspective, the device can request content fromthe server and receive one or more creatives for display. The clientdevice will also receive the targeted application webarchive. If or whena user interacts with the displayed creative, which links to thetargeted application, the client device can immediately launch thetargeted application because it had been optimistically downloaded.

The benefits of the manifest file to server can now be betterunderstood. Since the webarchive file is optimistically sent to thedevice, it is possible that the targeted application will never beneeded. Accordingly, the server can strike a balance between packagingand sending the primary resources of the targeted application, in casethey are needed, and wasting resources by sending a targeted applicationthat will never be launched on the client device. To strike this balancethe server packages only resources selected by the targeted applicationdeveloper and designated in the manifest file. All other applicationresources can be fetched on demand when needed.

Accordingly, the present technology provides a package structure which atargeted application developer can use to submit his/her application toa content server. Using the defined package structure, the server canprocess the content to be sent to client devices in an efficient mannerand a manner that preserves the intended operation of the targetedapplication as conceived by the content developer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a digital content bundle package structure;

FIG. 2 illustrates a flow chart for creating and delivering a mediapackage to a server;

FIG. 3 illustrates an exemplary display presenting a creative within aprimary application;

FIG. 4 illustrates an exemplary display presenting a creative within aprimary application in a portrait and landscape orientation;

FIG. 5 illustrates an interactive application and the screen applicationand closing of the creative in response to a user input; and

FIG. 6 is a schematic illustration of an exemplary system embodiment.

DESCRIPTION

The technology described herein relates to creating a digital contentbundle for ingestion into a content server. A content provider desiringto publish his/her content to the content server must package thecontent into a recognizable format that the content server can ingestand process into a format suitable for distribution to client devices.

FIG. 1 illustrates an example of a digital-content-package structureprepared by a content provider. The digital content package can includea properties file, one or more creatives and a targeted applicationaccompanied by a manifest file. The top-level directory of the packageis identified as “myApp” 102.

The “myApp” directory includes a properties file 104 that describesproperties of the digital content bundle. For example, one property inthe properties file 104 can include an “action” description. This“action” description defines what action will occur when a user input isreceived when a user clicks on a creative. Another property in theproperties file 104 can include an “initial orientation” that describesthe orientation in which a creative should be viewed in when itlaunches. A further property in the properties file 104 can include a“supported orientation” property that describes the orientations that agiven creative or the targeted application will support. Exemplaryvalues can include portrait, landscape, or all for both. Anotherproperty in the properties file 104 can include a “scrolling” propertythat describes if scrolling should be allowed for a creative or thetargeted application. Yet another property in the properties file 104can include a “background-color” property that describes a backgroundcolor for a creative or the targeted application. In one example, the“background-color” property is defined as a HEX value such as “7BA9C4”.

The properties file is not limited to describing the propertiesdescribed above. It should be appreciated that the properties file canbe used to describe any other property that the content developerdesignates. For example, the properties file can describe supporteddevices, content that the creatives or application can be associatedwith, properties regarding the targeted applications operation, display,use, etc. In some embodiments the properties file can also be used todescribe when a content developer envisions a creative might bedistributed to a client device. For example, certain creatives might bedesignated for distribution to specified smartphones, or for use withspecified applications or in specified contexts, etc.

The “myApp” directory also includes a folder for creatives 106 labeled“creatives” in FIG. 1. Each of the creatives can be applications orimages that link to a targeted application found in the “AppUnit”directory 112.

The “creatives” directory 106 illustrated in FIG. 1 includes, by way ofexample, a first creative “foo” 108 and a second creative “bar” 110. Asshown, first creative “foo” 108 contains an “HTMLBanner” folderincluding a file named “index.html” and a folder named “ImageBanners”.In one example, the “HTMLBanner” folder presents the HTML code for acreative, and the “ImageBanners” folder contains reveal images that aredisplayed during a transition from executing the creative to executingthe targeted application. In other examples, a creative can have only an“HTMLBanner” folder or “ImageBanners” folder.

Also, the second exemplary creative “bar” 110 also contains an“HTMLBanner” folder including a file named “index.html” and a foldernamed “ImageBanners”. As described above, in one example the“HTMLBanner” folder contains the HTML code for the creative, and the“ImageBanners” folder contains reveal images that are displayed during atransition from executing the creative to executing the targetedapplication. In other examples, a creative can have only an “HTMLBanner”folder or “ImageBanners” folder.

The digital content bundle also includes a targeted application“AppUnit” 112, which in most embodiments of the AppUnit application canbe presented in full screen. The targeted application “AppUnit” includesan index.html file 114, which in this example, constitutes the targetedapplication and a manifest file 116, but can also include additionalresources for use in association with the targeted application.

The manifest file 116 defines selected items that should be packagedwith the targeted application for distribution to a client device, suchas a smart phone. In some embodiments, the manifest file can alsocontain additional information, for example a command to compress theselected items to be packaged with the targeted application fordistribution into a single file. The manifest file 116, in oneembodiment, is a text file with paths for all resources to be includedin the webarchive. If a resource is included in the manifest file, italso should be included in the “myApp” directory. Additional items thatare not included in the manifest file can also be included in the“myApp” directory. A targeted application designer can choose whichitems are most important upon execution of the targeted application bylisting these items in the manifest file; all other items can bedownloaded after execution of the targeted application. This allowsapplication developers to strike a balance between content immediatelyavailable upon execution of the targeted application and deviceperformance characteristics such as speed and memory usage as willbecome more apparent from the description below.

In one example, the manifest file 116 can be formatted in the followingmanner: (1) The first line of the file must contain the manifest versionsuch as “Manifest-Version X.X”; (2) Comments are allowed. Comments canbe single line, start with a hash mark (#), and can appear on its ownline; (3) Each file or path must appear on a line of its own; (4) Allpaths are relative to the manifest file; (5) If the path points to adirectory, then the contents of that directory will be included in thewebarchive file; and (6) If the path points to a file, then that filewill be included in the webarchive file. This formatting is merelyillustrative and other formatting techniques can be implemented.

The package including 102, 104, 106, 108, 110, 112, 114, and 116 can becompressed into a single file and then sent to a server for ingestion bythe targeted application developer for distribution to client devices.

Upon ingesting, uncompressing, and analyzing the digital content packageincluding the manifest file 116, the server, to which the targetedapplication bundle is uploaded, will create a webarchive 118 next to themanifest 116 file as shown. The webarchive 118 will contain the selecteditems as defined in the manifest file that will be sent with theapplication to a user device. In a further example, the server cancreate a webarchive file for each creative (not shown).

FIG. 2 illustrates a flow chart for delivering the content packagedescribed above to a server and processing it to be available fordistribution to client devices. The method includes receiving, by theserver, one or more creatives 202 and a targeted application 204. Themethod further includes receiving a manifest file 206 that, as addressedabove, contains paths for selected files and folders for reference oruse by the targeted application archive. The method includes receiving adescriptive file with metadata 208. This descriptive file can be thesame as the properties file discussed above. The method then includescompressing the media package 210, and transmitting the compressed mediapackage for ingesting into the server.

At step 212, once the server has ingested the compressed media package,the server can uncompress the media package and check the package forerrors. This error checking process can include looking for properacceptable structure of the file and ensuring there are no missingvalues for the media package. The server can analyze the manifest file.This analysis of the manifest file can include sanitizing paths todescribe files listed in the manifest and other error detectiontechniques as needed. The server can also ignore paths that might causesecurity risks, such as paths that reference files that are not withinthe same folder or location as the manifest file.

Once the server completes any error detection, the method can includegenerating a webarchive file. In this example, the webarchive is creatednext to the manifest file 116. The webarchive contains the selectedfiles or folders as defined in the paths in the manifest file that willbe sent with the application to a user device. In one example, thefolders and files in the webarchive can be compressed to a single file.

In some embodiments, the method can include generating a webarchive filefor each creative in a content bundle. In this example, a webarchivefile for a creative can include all files needed to run the creative,which in such embodiments, is itself a targeted application, hereinaftercalled “creative application.” In some embodiments, each creativeapplication can have its own manifest file, to define selected items theserver should place in each archive file. In this example, the servercan create an archive file for a creative application in the samedirectory as its related manifest file.

In one example, the one or more creatives are in HTML and include adigital image. In another example, the one or more creatives can be asingle image. In another example, the creative application is in HTMLand includes a digital image.

The descriptive file with metadata can be in XML. The one or morecreatives can be advertisements. Also, the targeted application can bean advertisement.

After generating the webarchive file, the server can select particularportions of the media bundle, in response to a device request, and sendthose selected portions to a client device to run within a userapplication.

FIG. 3 illustrates an exemplary device 302 displaying a user application304 and a creative 306 in a view 308 within the user application 304. Asillustrated, the device 302 is a handheld computing device, for example,a smart phone, e.g., an IPHONE, by Apple Inc. of Cupertino, Calif.However, the device 302 can be any computing device such as a personalcomputer, laptop, tablet, or personal media-playing device; even ahousehold appliance having a processor and a display can be used withthe present technology.

The user application 304 can be any application that reserves a view 308or a window or a frame to display the creative 306. In some embodiments,the view has a standard dimension that is consistent across allpotential user applications. In some embodiments, the view 308 occupiesabout ten percent of the available screen area. Of course, the creativecan occupy any desired portion of the user application. However, thearea of the creative should not be so large as to obscure or detractfrom the user application, yet the creative should be large enough toview and interact with.

The creative 306 can be any image or application having content that iscreated with an audience in mind and can be targeted to that audience.For example, the creative can be a game for children; a web applicationtargeted at sports fans; or an advertisement for home improvementproducts targeted at home owners. In some preferred embodiments, thecreative 306 can have some relationship to the user application 304,such as a similarity in the target demographic for the audiences of bothapplications or in the nature of the content of the targetedapplications, etc.

Multiple creative configurations can be downloaded if the device hasmultiple possible presentation formats, such as portrait and landscape.In such aspects, it is anticipated that a view in portrait will not beas desirable in landscape. In some embodiments, it is desired that thecreative view and configuration occupy only about ten percent of thedisplay. As illustrated in FIG. 4, a creative in the portrait view (402)is fatter but thinner than the creative view in the landscape view(404). In the illustrated example, both views take up only about tenpercent of the available screen area.

When the device is in a first orientation, for example a portraitorientation, and then rotates to a second orientation, for example alandscape orientation, the creative view can resize along with the restof the user application, and the creative view configuration for thatorientation can be displayed. When the device is rotated into adifferent orientation, the user application will react to the change inorientation by rotating its view and resizing itself according to thenew orientation. A user application that can be displayed in bothlandscape and portrait orientations can download a targeted applicationthat can fit both orientations. When the device is rotated, the creativechanges shape and animates to show content appropriate to the new aspectratio. The content is still the same creative; it just has a slightlydifferent representation for the new aspect ratio.

After a creative and a targeted application are sent to a client device,the creative, running in a user application (502), can be interactiveand cause execution of the targeted application and closing of thecreative in response to a user input. As illustrated in FIG. 5, a usercan select the creative (504) using a pointing device (506). In theillustrated embodiment, the device has a touch screen input and thus afinger touch is illustrated, although any other selection mechanism isacceptable. Upon selection, the creative 504 causes execution ofapplication (508). At the left of FIG. 5, the creative is shown in view(504), while at the far right the targeted application (508) is runningdue to selection of the creative by a user. This application 508provides the full interactive content of a digital content bundle.

FIG. 6 illustrates a computer system 600 used in executing the describedmethod. Computer system 600 is an example of computer hardware,software, and firmware that can be used to implement disclosures above.System 600 includes a processor 620, representative of any number ofphysically and/or logically distinct resources capable of executingsoftware, firmware, and hardware configured to perform identifiedcomputations. Processor 620 communicates with a chipset 622 that cancontrol input to and output from processor 620. In this example, chipset622 outputs information to display 640 and can read and writeinformation to non-volatile storage 660, which can include magneticmedia and solid-state media, for example. Chipset 622 also can read datafrom and write data to RAM 670. A bridge 635 for interfacing with avariety of user interface components can be provided for interfacingwith chipset 622. Such user interface components can include a keyboard636, a microphone 637, touch detection and processing circuitry 638, apointing device, such as a mouse 639, and so on. In general, inputs tosystem 600 can come from any of a variety of sources, machine-generatedand/or human-generated.

Chipset 622 also can interface with one or more data network interfaces625 that can have different physical interfaces 617. Such data networkinterfaces can include interfaces for wired and wireless local areanetworks, for broadband wireless networks, as well as personal areanetworks. Some applications of the methods disclosed herein can includereceiving data over physical interface 617 or be generated by themachine itself by processor 620 analyzing data stored in memory 660 or670. Further, the machine can receive inputs from a user via devices636, 637, 638, 639 and execute appropriate functions, such as browsingfunctions, by interpreting these inputs using processor 620.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer-readable media. Such instructions comprise, forexample, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special-purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate-format instructions such as assembly language, firmware, orsource code, including transitory signals carrying the instructions.Examples of computer-readable media that may be used to storeinstructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware, and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality also can beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further, andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

The invention claimed is:
 1. A method comprising: receiving a digitalcontent package comprising a creative, a targeted application, and amanifest, the targeted application being associated with a plurality ofresources, and the manifest indicating a selected subset of theplurality of resources, wherein the selected subset is designated fromthe plurality of resources to be prepared for a single instance ofdistribution to a client device; error-checking the manifest, whereinerror-checking comprises by verifying proper structure of the resources,searching for missing values, and analyzing the manifest for securityrisks including removing paths to resources that are not included in thedigital content package; and preparing components of the digital contentpackage for distribution to the client device, wherein preparingcomponents of the digital content package comprises: storing datadescribing the devices for which the creative is targeted, the contentfor which the creative should be associated with, and the demographicsfor which the creative is targeted; generating a webarchive of thetargeted application and a selected file of the selected subset, theselected file being included in the webarchive based on the selectedfile's inclusion in the manifest; and storing the webarchive of thetargeted application in a directory on a server along with resourcesthat were not selected for inclusion in the webarchive; executing atargeted application testing program, wherein a webarchive is created toinclude the targeted application and the subset of resources identifiedin the manifest; receiving a selection of the creative; receiving aninput into the creative, the input being effective to cause execution ofthe targeted application from the webarchive; and receiving an inputinto the executed application, whereby a successful execution of thecreative confirms a performance of the webarchive creation, the targetedapplication and the creative in the testing program.
 2. The method ofclaim 1, wherein preparing the components of the digital content packagefor distribution to the client device further comprises identifying thecreative.
 3. The method of claim 2, wherein identifying the creativeincludes analyzing the creative and storing data describing thecreative, the data to be used in selecting which creative to send to theclient device.
 4. The method of claim 3, wherein the data to be used inselecting which creative to send to the client device comprises a listof available creatives.
 5. The method of claim 3, wherein the data to beused in selecting which creative to send to the client device comprisesdata describing devices for which the creative is targeted, content forwhich the creative should be associated with, and demographics for whichthe creative is targeted.
 6. A product comprising: a non-transitorycomputer-readable medium having a collection of computer-readable datastored thereon and being in a specified directory structure suitable forprocessing by a content server, the collection of computer-readable datacomprising: data defining a top-level directory; data making up adescriptive resource that is descriptive of various properties of atargeted application and a creative; data defining a first sub-directorylocated within the top-level directory storing the targeted applicationand its associated resources and a manifest identifying paths to thetargeted application and a subset of resources selected from among thetargeted application's associated resources, wherein the subset ofresources is designated from the application's associated resources tobe prepared for a single instance of distribution; data defining anerror-checking component of the manifest, wherein error-checkingcomprises verifying proper structure of the resources, searching formissing values, and analyzing the manifest for security risks includingremoving paths to resources that are not included in the targetedapplication and its associated resources; and data defining a secondsub-directory located within the top-level directory storing thecreative wherein the collection of computer-readable data causes acomputer to perform operations comprising: preparing a webarchiveincluding the targeted application and the subset of resourcesidentified in the manifest; and preparing the creative for distributionto client devices by examining the descriptive resource and storing dataindicative of the properties of the creative as provided by thedescriptive resource; storing data describing the devices for which thecreative is targeted, the content for which the creative should beassociated with, and the demographics for which the creative istargeted; generating a webarchive of the targeted application and aselected file of the selected subset, the selected file being includedin the webarchive based on the selected file's inclusion in themanifest; storing the webarchive of the targeted application in adirectory on a server along with resources that were not selected forinclusion in the webarchive; executing a targeted application testingprogram, wherein a webarchive is created to include the targetedapplication and the subset of resources identified in the manifest;receiving a selection of the creative; receiving an input into thecreative, the input being effective to cause execution of the targetedapplication from the webarchive; and receiving an input into theexecuted application, whereby a successful execution of the creativeconfirms a performance of the webarchive creation, the targetedapplication and the creative in the testing program.
 7. The product ofclaim 6, wherein the collection of computer-readable data causes acomputer to perform operations comprising: transmitting the creative toa client device in accordance with the stored data indicative of theproperties of the creative.
 8. The product of claim 6, wherein thecollection of computer-readable data causes a computer to performoperations comprising: transmitting the webarchive to a client device.9. A system comprising: a processor; and a non-transitorycomputer-readable storage medium having stored therein instructionswhich, when executed by the processor, cause the processor to performoperations comprising: receiving a digital content package including oneor more creatives, a targeted application, and a manifest, the targetedapplication being associated with a plurality of resources, and themanifest indicating a selected subset of resources, wherein the selectedsubset is designated from the plurality of resources to be prepared fora single instance of distribution to a client device; storing thedigital content package; error-checking the manifest by verifying properstructure of the resources, searching for missing values, and analyzingthe manifest for security risks including removing paths to resourcesthat are not included in the digital content package; preparingcomponents of the digital content package for distribution to the clientdevice, wherein preparing components of the digital content packagecomprises: storing data describing the devices for which the creative istargeted, the content for which the creative should be associated with,and the demographics for which the creative is targeted; generating awebarchive of the targeted application and selected files of the subsetof resources associated with the targeted application, the selectedfiles being included in the webarchive based on their inclusion in themanifest; storing the webarchive of the targeted application in adirectory on a server along with resources that were not selected forinclusion in the webarchive; executing a targeted application testingprogram, wherein a webarchive is created to include the targetedapplication and the subset of resources identified in the manifest;receiving a selection of the creative; receiving an input into thecreative, the input being effective to cause execution of the targetedapplication from the webarchive; and receiving an input into theexecuted application, whereby a successful execution of the creativeconfirms a performance of the webarchive creation, the targetedapplication and the creative in the testing program.
 10. The system ofclaim 9, wherein preparing the components of the digital content packagefor distribution to the client device further comprises identifying eachof the one or more creatives.
 11. The system of claim 10, whereinidentifying each of the one or more creatives includes analyzing thecreatives and storing data describing the creatives, the data to be usedin selecting which of the one or more creatives to send to the clientdevice.
 12. The system of claim 11, wherein the digital content packagefurther includes a properties file describing data to be used inselecting which of the one or more creatives to send to the clientdevice.
 13. The system of claim 12, wherein the data to be used inselecting which of the one or more creatives to send to the clientdevice comprises data describing devices for which one or more of thecreatives is optimized, content for which one or more of the creativesshould be associated with, and demographics for which one or more of thecreatives are optimized.